Hi,
We have both a DOORS 7.1 and a DOORS 9.3 database server running. We are now in the process of integrating the 7.1 data into the 9.3 server.
Reading the documentation on the topic recommends the data just to be copied to the 9.3 data directory (and restart the 9.3 server). But that's not possible for us since there are already data in the 9.3 database, and it will be overwritten if we just copy...
There also seems to be a way "archive and restore", but with loss of access control and project links.
My question is simply, how can I import the 7.1 data into a 9.3 database where there already is data?
And at the same time keeping access control, links etc?
/Peter
pelig - Thu Feb 09 05:34:49 EST 2012 |
|
Re: Howto import Doors 7.1 data into existing 9.3?
llandale - Thu Feb 09 13:31:28 EST 2012
As for maintaining links: In the v7 database you can create a single project "Archive" and move all the other project under it. Then archive-restore that one big project. That will retain the links. Perhaps though its too big for that.
As for maintaining access rights: That would be very difficult. User "Joe" in db1 may have user ID 4, and "Joe" in db2 may have ID 6. Access records are stored with the IDs (so you can rename Joe to Jane and retain the rights), it would be touph to translate the access rights. Perhaps dump all the access records in v7, and use some DXL to read that file and apply those accesses to the new project.
If the v9 database is the small one, then perhaps archive all the v9 projects as above, "migrate" the v7 database effectively erasing the v9, then restore the v9 projects. You would need then to establish the new v9 users, and restore those project's access rights.
-Louie
|
|
Re: Howto import Doors 7.1 data into existing 9.3?
SystemAdmin - Fri Feb 10 08:54:48 EST 2012 llandale - Thu Feb 09 13:31:28 EST 2012
As for maintaining links: In the v7 database you can create a single project "Archive" and move all the other project under it. Then archive-restore that one big project. That will retain the links. Perhaps though its too big for that.
As for maintaining access rights: That would be very difficult. User "Joe" in db1 may have user ID 4, and "Joe" in db2 may have ID 6. Access records are stored with the IDs (so you can rename Joe to Jane and retain the rights), it would be touph to translate the access rights. Perhaps dump all the access records in v7, and use some DXL to read that file and apply those accesses to the new project.
If the v9 database is the small one, then perhaps archive all the v9 projects as above, "migrate" the v7 database effectively erasing the v9, then restore the v9 projects. You would need then to establish the new v9 users, and restore those project's access rights.
-Louie
However, I solved it by adding a second database server service, where the data for the second service is on a different path.
(I used the "doorsd.exe -minstall -p <port> -s <path>" command)
Perhaps later I will integrate the two databases into one, using the instructions from llandale. This should be easier since they both are in 9.3 format.
But now have a problem with setting up the DOORS Web Access to find my second database repository. See this thread and please answer if you have any ideas:
https://www.ibm.com/developerworks/forums/thread.jspa?threadID=417732
(BTW I had to change my IBM-ID from pelig->pelig99 due to some mail collision or...something strange...)
/Peter
|
|